Budget information system with cross-reference feature and related methods

ABSTRACT

A budget information device may include a memory and a processor cooperating with the memory for importing and storing different financial databases into the memory. Each different financial database may include numerical data and textual identifiers. The processor and memory may be for processing the numerical data and textual identifiers from the different financial databases. The processor and memory may also be for providing a GUI to a user, the GUI including views for respectively accessing the numerical data and textual identifiers for each of the different financial databases. Each view may include a cross-reference feature for accessing numerical data and textual identifiers associated to numerical data and textual identifiers in a current view.

RELATED APPLICATIONS

This application is divisional of U.S. patent application Ser. No.13/795,995 filed on Mar. 12, 2013 which claims the benefit ofprovisional application Ser. No. 61/665,692 filed Jun. 28, 2012, whichare hereby incorporated herein in their entirety by reference.

FIELD OF THE INVENTION

The present invention relates to the field of processing a networkedprocessing system, and, more particularly, to a system for remotelyviewing the budgetary data and related methods.

BACKGROUND OF THE INVENTION

Government budgets are typically quite complex and extensive in scope.For example, the State of Florida has fiscal year 2013 budget of $70billion spread across many agencies. Initially, when the budgets werefirst digitized, there was little standardization and littletransparency. In other words, only those with an intimate understandingof the budget could distill anything more than generalities.

Eventually, accounting codes were standardized in the State of FloridaBudget, which aided in the digitization across different agencies.Nevertheless, each agency maintained their budget system individually,leading to reduced interoperability. These budget systems were oftenhoused on mainframes, with program files being difficult to access andmanipulate. Another drawback to these individualized systems was thattheir use required extensive training and a background in the budgetsystem. For elected officials, a staff was required to mine data asdesired. Moreover, for a person outside the government, it would bevirtually impossible to obtain such data in a desired form.

In the State of Florida system, operational systems data for statepersonnel, accounting, budgeting, planning, and contracts are housed inseparate mainframe computers that are not linked together and areincompatible. With recent laws, many governmental entities are nowobligated to provide public access to many of these same budget systems.Moreover, this same access may need to be provided in an onlineinterface that may be navigated by the public.

SUMMARY OF THE INVENTION

Generally speaking, a budget information device (or an electronicdevice) may include a memory and a processor cooperating with the memoryfor importing and storing a plurality of different financial databasesinto the memory, each different financial database comprising numericaldata and textual identifiers (e.g. monetary cost and item description).The memory and a processor may also be for processing the numerical dataand textual identifiers from the plurality of different financialdatabases, and providing a graphical user interface (GUI) to a user, theGUI (e.g. web page based user interface) comprising a plurality of viewsfor respectively accessing the numerical data and textual identifiersfor each of the plurality of different financial databases, each viewcomprising a cross-reference feature for accessing numerical data andtextual identifiers associated to numerical data and textual identifiersin a current view. Advantageously, the budget information deviceenhances the transparency of the financial data therein for the user.

In particular, the cross-reference feature may provide a pop-up windowcomprising a plurality of tabs for accessing the numerical data andtextual identifiers in respective different financial databasesassociated to the numerical data and textual identifiers in the currentview. Each view may comprise a menu comprising a plurality of fiscalyear indicators for providing the numerical data and textual identifiersfor each fiscal year.

In some embodiments, each view may comprise a home screen providing ageneral overview of the numerical data and textual identifiers for thecorresponding different financial database. For example, the pluralityof different financial databases may comprise a planning database, abudget database, an accounting database, a personnel database, and acontracts database. Also, the view for the budget database may comprisea plurality of tabs for accessing a plurality of versions of a budget.

The GUI may comprise a plurality of tabs for selecting the plurality ofviews for accessing the numerical data and textual identifiers for theplurality of different financial databases. Moreover, the GUI mayprovide a tracking view comprising numerical data and textualidentifiers for a plurality of user-selected items, and the processormay update the numerical data and textual identifiers for the pluralityof user-selected items from the plurality of different financialdatabases.

Another aspect is directed to a budget information system comprising aplurality of different financial databases, and a budget informationdevice remote to the plurality of different financial databases andcomprising a memory and a processor cooperating with the memory. Theprocessor and the memory may be for importing and storing the pluralityof different financial databases into the memory, each differentfinancial database comprising numerical data and textual identifiers,processing the numerical data and textual identifiers from the pluralityof different financial databases, and providing a GUI to a user. The GUImay comprise a plurality of views for respectively accessing thenumerical data and textual identifiers for each of the plurality ofdifferent financial databases. Each view may comprise a cross-referencefeature for accessing numerical data and textual identifiers associatedto numerical data and textual identifiers in a current view.

Another aspect is directed to a method for displaying budget informationfrom a plurality of different financial databases. The method maycomprise using a memory and a processor cooperating with the memory forimporting and storing the plurality of different financial databasesinto the memory, each different financial database comprising numericaldata and textual identifiers, processing the numerical data and textualidentifiers from the plurality of different financial databases, andproviding a GUI to a user. The GUI may comprise a plurality of views forrespectively accessing the numerical data and textual identifiers foreach of the plurality of different financial databases. Each view maycomprise a cross-reference feature for accessing numerical data andtextual identifiers associated to numerical data and textual identifiersin a current view.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of an embodiment of a budget informationsystem, according to the present invention.

FIGS. 2-24 are screenshots from the GUI provided by the budgetinformation system of FIG. 1.

FIG. 25 is a schematic diagram of an exemplary application for thebudget information system of FIG. 1.

FIG. 26 is another schematic diagram of an exemplary application for thebudget information system of FIG. 1.

FIG. 27 is a flowchart illustrating operation of an exemplaryapplication for the budget information system of FIG.

FIGS. 28-44 are additional screenshots from the GUI provided by thebudget information system of FIG. 1.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The present invention will now be described more fully hereinafter withreference to the accompanying drawings, in which preferred embodimentsof the invention are shown. This invention may, however, be embodied inmany different forms and should not be construed as limited to theembodiments set forth herein. Rather, these embodiments are provided sothat this disclosure will be thorough and complete, and will fullyconvey the scope of the invention to those skilled in the art. Likenumbers refer to like elements throughout.

Referring now to FIG. 1, a budget information system 100 according tothe present invention is now described. The budget information system100 illustratively includes a plurality of different financial databases113 a-113 c, and a budget information device 110 remote to the pluralityof different financial databases and comprising a memory 111 and aprocessor 112 cooperating with the memory. For example, the budgetinformation device 110 may comprise a web-based server comprising arelational database server, such as a Microsoft SQL Server, as availablefrom the Microsoft Corporation of Redmond, Wash.

For example, the plurality of different financial databases 113 a-113 cmay comprise a planning database, a budget database, an accountingdatabase, a personnel database, and a contracts database. In someembodiments (FIGS. 2-44), these different financial databases 113 a-113c may be related to governmental entities, such as the State of Florida.

The processor 112 and the memory 111 illustratively import and store theplurality of different financial databases 113 a-113 c into the memory.In particular, each different financial database 113 a-113 c comprisesnumerical data and textual identifiers, and this data is stored in thememory 111. The numerical data and textual identifiers may comprisemonetary cost and item description. The processor 112 and the memory 111may import and store the plurality of different financial databases 113a-113 c into the memory using the approach disclosed in U.S. Pat.6,687,713 to Mattson et al., also assigned to the present application'sassignee, the contents of which are incorporated by reference in theirentirety.

The processor 112 and the memory 111 illustratively process thenumerical data and textual identifiers from the plurality of differentfinancial databases 113 a-113 c. In particular, the budget informationdevice 110 is networked (e.g. local networking or Internet based) withthe different financial database 113 a-113 c and retrieves the numericaldata and textual identifiers therefrom. Since the numerical data andtextual identifiers may change, the budget information device 110 mayperiodically pull this data from the different financial databases 113a-113 c, such as on a weekly basis. The budget information device 110may import the entirety of the different financial databases 113 a-113 cinitially and thereafter only pull delta (i.e. difference) data, therebyreducing traffic load.

The budget information system 100 illustratively includes a computingdevice 114 (e.g. a web enabled device, such as the illustrated personalcomputing device, a mobile cellular device, a tablet computing devicefor use by a user). The processor 112 and the memory 111 illustrativelyprovide a GUI to a user on the computing device 114. The computingdevice 114 would comprise a display, and a processor cooperatingtherewith to render the GUI on the display. For example, the GUI maycomprise a HyperText Markup Language (HTML) GUI, which can be readilyviewed on a great variety of devices.

Referring now additionally to FIGS. 2-9, the GUI is now described indetail. In this exemplary illustrated embodiment, the GUI provides datarelated to the State of Florida, but is can be readily appreciated thatthe herein described system can be used for many other financialdatabases (e.g. National Government Entities, large corporate entities,etc.). The GUI comprises a plurality of views 120, 140, 160, 180, 200,220, 240 for respectively accessing the numerical data and textualidentifiers for each of the plurality of different financial databases113 a-113 c. Each view 120, 140, 160, 180, 200, 220, 240 defines amodule for the respective different financial database 113 a-113 c. Themodule may comprise a plurality of levels as the user navigates the dataof the associated financial database 113 a-113 c. Each level in themodule represents a corresponding tier of data (i.e. tiers correspondingto levels of the entity, e.g. department, agency, office, divisionrepresenting levels) in the respective different financial database 113a-113 c. In the illustrated embodiment, each view 120, 140, 160, 180,200, 220, 240 comprises a home screen providing a general overview ofthe numerical data and textual identifiers for the correspondingdifferent financial database 113 a-113 c.

Each view 120, 140, 160, 180, 200, 220, 240 comprises a cross-referencefeature 260 for accessing numerical data and textual identifiersassociated to numerical data and textual identifiers in a current view.In other words, whatever data being viewed by the user in the currentview can be readily referenced to related data in other modules. Forexample, using the State of Florida embodiment, if the user is viewingthe budget data for a particular program, the user can easily in oneclick view the contracts executed for the same program, the planningdata for the same program, the personnel associated to the program, andthe accounting results for the same program.

In particular, the cross-reference feature 260 illustratively provides apop-up window 300 comprising a plurality of tabs 302-306 for accessingthe numerical data and textual identifiers in respective differentfinancial databases 113 a-113 c associated to the numerical data andtextual identifiers in the current view. Advantageously, the user cannavigate the cross-referenced data across each module without leavingthe current view. Each view may comprise a menu 142 comprising aplurality of fiscal year indicators for providing the numerical data andtextual identifiers for each fiscal year.

Each view 120, 140, 160, 180, 200, 220, 240 of the GUI illustrativelyincludes a plurality of tabs 91-97 for selecting the plurality of viewsfor accessing the numerical data and textual identifiers for theplurality of different financial databases 113 a-113 c. These tabs 91-97are global and accessible in every view 120, 140, 160, 180, 200, 220,240 and level. Also, each view 120, 140, 160, 180, 200, 220, 240 of theGUI illustratively includes a global locater 101 for providing the usera quick reference to the current view's location in the databasenavigation. The global locater 101 provides the user with a module andtier of current location in the financial database 113 a-113 c.

In FIG. 2, the view 120 for the home page is shown. This view 120illustratively includes a welcome message panel 723, and a data sourcespanel 121 providing a short description of each of the accessibledifferent financial databases 113 a-113 c. Moreover, the data sourcespanel 121 provides duplicative links for selecting the plurality ofviews 120, 140, 160, 180, 200, 220, 240 for accessing the numerical dataand textual identifiers for the plurality of different financialdatabases 113 a-113 c.

In FIG. 3, the view 140 for the planning financial database (planningmodule) is shown. This view 120 illustratively includes a welcomemessage panel 711, and a general overview panel 141 including generalaggregate data for each major governmental division of the State ofFlorida. In the general overview panel 141, each section provides a linkto the appropriate data in the planning database. Also, the view 140illustratively includes a menu feature 142 for providing access to thenumerical data and textual identifiers for varying fiscal years. Thisfeature is advantageously included in some of the other views.

In FIG. 4, the view 160 for the planning financial database (module) isshown. This view 160 illustratively includes a welcome message panel712, and a general overview panel 161 including aggregate expendituresfor each major governmental division of the State of Florida. In FIG. 5,the view 180 for the personnel financial database (module) is shown.This view 180 illustratively includes a welcome message panel 713, and ageneral overview panel 181 including aggregate personnel expenditures,positions, and position vacancies for each major governmental divisionof the State of Florida.

In FIG. 6, the view 200 for the contracts financial database (module) isshown. This view 200 illustratively includes a welcome message panel714, again providing some general contracts database information to theuser. This view 200 illustratively includes a general overview panel 201including aggregate contract expenditures, and the number of annualcontracts for each major governmental division of the State of Florida.

In FIGS. 7-8, the view 220 for the tracking feature (i.e. tracking viewor tracking module) is shown. This view 220 illustratively includesnumerical data and textual identifiers for a plurality of user-selecteditems. In particular, as the user explores the varying levels of the GUIand the modules therein, the user may find a particular item ofinterest. The user may utilize the tracking feature and “favorite” theitem, which links the item to the tracking view 220. The processor 112updates the numerical data and textual identifiers for the plurality ofuser-selected items from the plurality of different financial databases113 a-113 c. The first level view 220 illustratively includes a list ofuser created folders 224. It should be appreciated that although onlyone folder is illustrated, the GUI is capable of providing many more.The view 220 also includes a menu feature 222 for selecting the usercreated folders. Of course, the user may also directly select the folder224. Once the user selects the folder 224, the next view 221 (lowerlevel view) provides a listing of the plurality of user-selected items223 a-223 c within the folder 224. Advantageously, if the user isinterested in a particular program associated with local schools, theuser may track this program and monitor each stage of the program, i.e.budget appropriations, contracts executed on its behalf, personnelworking on it, actual accounting for the program, and planning documentsfor the program.

In FIGS. 9-10, the view 240 for the budget financial database (module)is shown. In the following, several levels of the budget module are nowdescribed for exemplary purposes. Many of the features disclosed for thebudget module may be applied to the other modules disclosed herein. Thisview 240 illustratively includes a welcome message panel 715 providingconglomerate budget data and direct links to popular budget data items,illustratively funding comparisons, budget bills, and all budgetdetails. This view 240 illustratively includes a general overview panel241 including aggregate budget amounts, and positions for each majorgovernmental division 241-246 of the State of Florida. As noted above,this view 240 also includes the menu feature 142 for selecting the datafor different fiscal years. Additionally, this view 249 illustrativelyincludes a menu feature 249 for selecting varying versions of the budgetdata in the current view. In the illustrated embodiment, the versionsinclude an agency requested version, a Governor's recommendationversion, and a Senate version.

As in other views, each of the major governmental division 241-246 inthe general overview panel 241 may be selected for navigating theassociated data. After selection of the education division 246, the GUIprovides a second level view 250 of the education budget information.This view 250 includes the same global menu features 142, 249, and apanel 251 including the education budget information. The educationbudget information illustratively includes a list of programs 252 a-252n. The view 250 also includes a search feature 265 for providing theuser quick access to specific budget data. Positively, at any point, theuser may key word search the current view's module for the relevantdata.

Referring now additionally to FIG. 11, this view 250 illustrativelyincludes the cross-reference feature 260 for accessing numerical dataand textual identifiers associated to numerical data and textualidentifiers in a current view, and the aforementioned tracking feature267. In particular, the cross-reference feature 260 illustrativelyincludes links (icons) 261-264 for each of the other different financialdatabases 113 a-113 c not currently being viewed. In this illustratedexample, the links include a planning link 261, an accounting link 262,a personnel link 263, and a contracts link 264. Helpfully, the programsand data in the current view can quickly be related to associated datain the other different financial databases 113 a-113 c.

In FIG. 12, the GUI provides a third level view 270 of the educationbudget information. In particular, this view 250 is provided after theselection of the “education-fixed capital outlay” program link in theupper level view 250. This view 270

illustratively includes a panel 276 comprising a list of issues 275a-275 d related to the “education-fixed capital outlay,” and the relatedbudget data (i.e. issue code, conference committee amount, positions,agency request amount, Governor's amount, and the Senate amount). Inaddition, the panel 276 illustratively includes a plurality of tabs271-273 for accessing base budget data, and new issues.

In FIG. 13, the GUI provides a fourth level view 280 of the educationbudget information. In particular, this view 280 is provided after theselection of the “debt service” link in the upper level view 270. Also,this view 280 illustratively includes a panel 281 providing datarelating to the “debt service.” Advantageously, this panel 281illustratively includes a plurality of tabs 283-289 for accessing aplurality of versions of a budget and narratives relating to the item.This view 280 also includes forward and backward buttons 279 a-279 b forreadily navigating data related to list 275 a-275 d in the upper levelview 270. The plurality of versions of the budget comprises an agencyversion 283, a Governor's recommendation version 284, a pending Housebill version 285, a Senate bill version 286, a pending conference bill287, an agency narrative 288, and a Governor's narrative 289.Advantageously, the user can quickly switch between varying versions ofthe State of Florida's budget, thereby enabling the user to readilypierce the obfuscation of the budgetary process. The pending House billand the pending conference bill tabs 285, 287 are grayed out since theseversions are unavailable. In particular, the budget information device110 accessed the appropriate different financial databases 113 a-113 cand determined that there was no pending House committee data related tothis item, and this is presented to the user via the grayed out tabs.Referring to FIGS. 14-16, the view 280 changes as the user cyclesthrough the plurality of tabs 283-289. That is, the view 280 isproviding access to the plurality of versions of the budget andnarratives relating to the item.

Now referring to FIGS. 17-18, once the cross-reference feature 260 isselected, the view 280 now illustratively includes a pop-up window 300comprising a plurality of tabs 302-306 for accessing the numerical dataand textual identifiers in respective different financial databases 113a-113 c associated to the numerical data and textual identifiers in thecurrent view 280. Helpfully, the user is navigated by default to the tab302-306 related to the link 261-264 selected in the cross-referencefeature 260. The pop-up window 300 illustratively includes a menu 301comprising a plurality of fiscal year indicators for providing thecross-referenced numerical data and textual identifiers for each fiscalyear (FIG. 17: 2012-2013, FIG. 18: 2011-2012).

Referring to FIGS. 19-20 & 22-23, the view 280 changes as the usercycles through the plurality of tabs 302-306. That is, the view 280 isproviding access to the cross-referenced data in each of the differentfinancial databases 113 a-113 c. In particular, FIG. 20 shows theversion of the pop-up window 300 including the cross-referenced datafrom the accounting database. Furthermore, with reference additionallyto FIGS. 21 & 24, the user may select the displayed item 308 in thepop-up window 300, which quickly navigates the user to the appropriatedata in the accounting view (module) 320. This view also illustrativelyincludes a search feature 325 for quick access to desired data. Anotherview 340 shows the result of the selection of item 347 in the contractstab 306 in the pop-up window 300. In this view 340, the user has beennavigated to the appropriate location in the contracts database foraccess. This contracts view 340 also illustratively includes a searchfeature 342 for providing access to desired data in the contractsdatabase. This view 340 also includes a panel 341 for providing adetailed view of the cross-referenced data item 347.

Another aspect is directed to a method for displaying budget informationfrom a plurality of different financial databases 113 a-113 c. Themethod may comprise using a memory 111 and a processor 112 cooperatingwith the memory for importing and storing the plurality of differentfinancial databases 113 a-113 c into the memory, each differentfinancial database comprising numerical data and textual identifiers,processing the numerical data and textual identifiers from the pluralityof different financial databases, and providing a GUI to a user, the GUIcomprising a plurality of views 120, 140, 160, 180, 200, 220, 240 forrespectively accessing the numerical data and textual identifiers foreach of the plurality of different financial databases. Each view 120,140, 160, 180, 200, 220, 240 comprises a cross-reference feature 260 foraccessing numerical data and textual identifiers associated to numericaldata and textual identifiers in a current view.

Referring now to FIG. 25, a schematic diagram 400 shows the budgetinformation device 110 accumulating the needed data for a budgetfinancial database 401. In particular, the budget financial database 401illustratively includes an agency request database 113 a, a Governor'sbudget database 113 b, a House budget database 113 c, a Senate budgetdatabase 113 d, and a conference committee budget database 113 e, aplanning database 113 f, an accounting database 113 g, a personneldatabase 113 h, and a contracts database 113 i. In this illustratedembodiment, the budget information device 110 is accessing each of theneeded financial databases of the State of Florida to provide thecomprehensive data to the user.

Referring now to FIG. 27, a flowchart 430 shows a method for the budgetinformation device 110 accumulating data. As an initial premise anddividing logic, there are a plurality of policy groups, each comprisingdepartments (i.e. state agencies), and each department comprises aplurality of divisions (Blocks 431, 433, 435). Each department comprisesa plurality of budget entities 437 a-437 c, each providing appropriatefinancial data to the databases 113 a-113 c (Blocks 438-439, 441, 443).In this illustrated embodiment, the databases comprise an Office ofProgram Policy Analysis and Government Accountability (OPPAGA) database438, a Legislative Appropriations System (LAS)/Planning Budget Subsystem(PBS) database 439, a Florida Accounting Information Resource Subsystem(FLAIR) database 441, and a People First Subsystem (PFS) database 443.As will be appreciated, these databases 438-439, 441, 443 are madepublic and accessible due to demands of transparency laws in the Stateof Florida. The budget information device 110 mines each of thesedatabases and generates a planning database 445, a budget database 447,a personnel database 449, a contracts database 451, and an accountingdatabase 453. The budget information device 110 may generate a trackingdatabase 454 based upon the selections from the tracking feature 267noted above, and may generate a budget projection database 457 basedupon the mined data.

Referring now to FIG. 26, a schematic diagram 410 shows exemplarydatabases (State of Florida) that the budget information device 110 mayaccess to provide the data for the GUI. In particular, the data from theview 140 of planning (module) data is derived from a PBS 411; the datafrom the view 280 of budget (module) data is derived from a LAS/PBS 412;the data from the view 160 of accounting (module) data is derived from aFLAIR 413; the data from the view 180 of personnel (module) data isderived from a PFS 414 (i.e. OPS data from FLAIR); and the data from theview 200 of contracts (module) data is derived from a State ContractManagement System (SCMS) and Department of Transportation (DOT) system415.

The cross-reference 260 feature permits a user to seamlessly navigateacross the State of Florida's separate systems, represented inTransparency 2.0 by the five main modules (views): Planning, Budget,Accounting, Personnel and Contracts. Data for these five modules isstored on completely separate computer platforms within State of Floridagovernment. The cross-reference feature 260 permits the vertical andhorizontal data mining of systems and data stored on these otherwiseindependent information sources. One way to visualize the full potentialand power of the Cross Reference feature within Transparency 2.0 is tothink of the state government's data as being held in five separatesilos, each a separate and independent computer system. Transparency 2.0seamlessly integrates these five separate systems of government andgives the user tools to research, compare and analyze this information,all from a single source.

The potential key to cross-referencing the data is the codes used acrossall systems, primarily the budget entity. The following Table 1 displaysthe key codes or fields that are shared between modules or are unique toa particular module.

TABLE 1 Codes and Fields Shared Between Modules Budget Budget PlanningBill Details Accounting Personnel Contracts Fiscal Year X X X X X XSection X X Budget Entity* X X X X X X Appropriation Category X X X XFund X X X Fund Source X X Issue Type X X Issue Code X X Object Code XContract No. X X Dollars X X X X X FTE/Position Data X X X

By using the cross-reference feature 260, the user can view how theresources of the State of Florida are being planned and managed(Planning), what funds are being requested and budgeted (Budget), howand where the tax dollars are being spent (Accounting), who makes up theState's workforce (Personnel), and who benefits from state contracts(Contracts) by moving quickly from one module to the next all within onewindow.

Referring now additionally to FIGS. 28-31, the view 250 of the budgetdata with annotations is shown. The cross-reference feature 260 andassociated pop-up window 300 is accessed via the icons therein (dashedlines connecting the icon to the appropriate cross-reference tab302-206). There are five cross-reference icons representing the fivemain modules of data located directly below the Summary Grid for allmodules except Planning.

Once the planning tab 302 is selected, the user is navigated to the view480 of the planning data (view 480 split between FIGS. 30 & 31). Again,the view 480 illustratively includes a search feature 481 for accessingdesired data. For the Planning Module the cross-reference feature 260 islocated directly below the header bar.

As the user drills down through agencies and individual programs, thecross-reference feature 260 remains available to show the user veryspecific data from other modules as it relates to the Budget Group,Agency, or Program (i.e. tier of government) that is currently beingviewed. If the user finds something of interest that may warrant furtherexamination, the user need only click on the entry and be taken to thatspecific data area within another module.

Referring now to FIGS. 29-44, the following are examples for each of thefive modules with a screen shot displaying the information that can beviewed from within the cross-reference pop-up window 300, from any ofthe other modules, and then a comparison screen shot of the sameinformation that would be viewed by going directly to that module. Allexamples are for the Health Care Regulation program (code 68700700) inthe Agency for Health Care Administration.

FIGS. 29-31 demonstrate the cross-reference to Planning Module. FIG. 32shows a pop-up window 510 with cross-reference data. By selecting thebudget tab 515 (circled), the user is navigated to the budget view 520(FIG. 33). This view 520 from the budget module illustratively includesa list of items for totals by program. By selecting item “health careregulation” 525, the user navigates one level lower in the budget module(FIG. 34).

FIG. 34 includes a view 530 from the budget module that lists the budgetissues for the selected program. FIG. 35 shows a pop-up window 540 fromselecting the cross-reference feature 260 of the view 530. By selectingthe accounting tab 545 (circled), the user is navigated to the budgetview 550 (FIG. 36). By selecting the “Health Care Regulation” item 551,the user is navigated to another lower level view 560. This view 560includes a panel 565 showing conglomerate expenditure for the selectedprogram, and another panel 566 including a list of items and associatedexpenditures and item codes. The panel 566 also includes a menu 567 forselecting the viewing arrangement of the list of items. Either the usermay view the information based upon the object codes or the vendor.FIGS. 31-38 show views demonstrating the data switching between objectcode and vendor views, respectively 560, 570.

FIGS. 39-40 show a view 590 for demonstrating the cross-reference to thepersonnel module. The cross-reference pop-up window 580 illustrativelyincludes a plurality of tabs, including a personnel tab 585. Byselecting the personnel tab 585, the user is navigated to the personnelmodule (FIG. 40) of the GUI.

The view 590 illustratively includes a menu 596 for showing differingtypes of positions, namely: all, salaried, vacant, and Other PersonalServices Employment (OPS), i.e. at-will employment. In other words, onethe user has navigated to the personnel module data related to theprogram of interest, the user may quickly sort the positions.Additionally, the personnel view 590 illustratively includes a searchfeature 595. By selecting item 598 in the view 590, the user isnavigated to view 600 (FIG. 41) in the personnel module. This view 600illustratively includes a panel 605 providing detailed financial data onthe personnel for the related item. By stepping through the contractstab 612 in the cross-reference data pop-up window 610 (FIG. 42), theuser is navigated to a view 620 (FIG. 43) in the contracts module.

Now, by selecting item 621 in view 620, the user is navigated to view630. This view 630 includes a general information panel 631 providingconglomerate contract amounts and numbers thereof, and a second panel632. The second panel 632 includes contracts for specific programs.

Many modifications and other embodiments of the invention will come tothe mind of one skilled in the art having the benefit of the teachingspresented in the foregoing descriptions and the associated drawings.Therefore, it is understood that the invention is not to be limited tothe specific embodiments disclosed, and that modifications andembodiments are intended to be included within the scope of the appendedclaims.

That which is claimed is:
 1. A budget information device in a budgetinformation system including a plurality of computer systems configuredto respectively store and maintain a plurality of different financialdatabases, each different financial database being associated with arespective organizational entity, the budget information devicecomprising: a memory and a processor cooperating with said memory, saidprocessor configured to communicate with the plurality of computersystems, and importing and storing the plurality of different financialdatabases into said memory, each different financial database comprisingdifferent numerical data and textual identifiers, the differentnumerical data and textual identifiers for each different financialdatabase being different from other numerical data and textualidentifiers in other different financial databases, process thedifferent numerical data and textual identifiers from the plurality ofdifferent financial databases, provide a graphical user interface (GUI)to a user, the GUI comprising a plurality of menus for respectivelyaccessing the different numerical data and textual identifiers for eachof the plurality of different financial databases, each menu comprisinga cross-reference icon for accessing numerical data and textualidentifiers in other different financial databases and associated tonumerical data and textual identifiers in a current menu, for each menu,a plurality of vertical sub-menu levels corresponding to a plurality ofdivisional levels within the respective organizational entity, eachvertical sub-menu level comprising a sub-menu cross-reference icon foraccessing numerical data and textual identifiers in other differentfinancial databases and associated to numerical data and textualidentifiers in a current vertical sub-menu, and a tracking menucomprising different numerical data and textual identifiers for aplurality of user-selected items, use shared codes and fields from eachof the plurality of different financial databases to generate thenumerical data and textual identifiers in the other different financialdatabases and associated to the numerical data and textual identifiersin the current menu, and update the different numerical data and textualidentifiers for the plurality of user-selected items from the pluralityof different financial databases.
 2. The budget information device ofclaim 1 wherein the cross-reference icon provides a pop-up windowcomprising a plurality of tabs for accessing the numerical data andtextual identifiers in respective different financial databasesassociated to the numerical data and textual identifiers in the currentmenu.
 3. The budget information device of claim 1 wherein each menucomprises a plurality of fiscal year indicators for providing differentnumerical data and textual identifiers for each fiscal year.
 4. Thebudget information device of claim 1 wherein each menu comprises a homescreen providing a general overview of the different numerical data andtextual identifiers for the corresponding different financial database.5. The budget information device of claim 1 wherein the plurality ofdifferent financial databases comprises a planning database, a budgetdatabase, an accounting database, a personnel database, and a contractsdatabase.
 6. The budget information device of claim 5 wherein the menufor the budget database comprises a plurality of tabs for accessing aplurality of versions of a budget.
 7. The budget information device ofclaim 1 wherein said GUI comprises a plurality of tabs for selecting theplurality of menus for accessing the different numerical data andtextual identifiers for the plurality of different financial databases.8. The budget information device of claim 1 wherein the differentnumerical data and textual identifiers comprise a monetary cost and itemdescription.
 9. The budget information device of claim 1 wherein saidGUI comprises a web page based user interface.
 10. The budgetinformation device of claim 1 wherein the plurality of differentfinancial databases comprises an Office of Program Policy Analysis andGovernment Accountability (OPPAGA) database, a LegislativeAppropriations System (LAS)/Planning Budget Subsystem (PBS) database, aFlorida Accounting Information Resource Subsystem (FLAIR) database, anda People First Subsystem (PFS) database.
 11. An electronic devicecomprising: a memory and a processor cooperating with said memory, saidprocessor configured to communicate with a plurality of computersystems, and importing and storing a plurality of different financialdatabases from the plurality of computer systems and into said memory,each different financial database being associated with a respectiveorganizational entity and comprising different numerical data andtextual identifiers, the different numerical data and textualidentifiers for each different financial database being different fromother numerical data and textual identifiers in other differentfinancial databases, process the different numerical data and textualidentifiers from the plurality of different financial databases, providea graphical user interface (GUI) to a user, the GUI comprising aplurality of menus for respectively accessing the different numericaldata and textual identifiers for each of the plurality of differentfinancial databases, each menu comprising a cross-reference icon foraccessing numerical data and textual identifiers in other differentfinancial databases and associated to numerical data and textualidentifiers in a current menu, for each menu, a plurality of verticalsub-menu levels corresponding to a plurality of divisional levels withinthe respective organizational entity, each vertical sub-menu levelcomprising a sub-menu cross-reference icon for accessing numerical dataand textual identifiers in other different financial databases andassociated to numerical data and textual identifiers in a currentvertical sub-menu, and a tracking menu comprising different numericaldata and textual identifiers for a plurality of user-selected items, useshared codes and fields from each of the plurality of differentfinancial databases to generate the numerical data and textualidentifiers in the other different financial databases and associated tothe numerical data and textual identifiers in the current menu, andupdate the different numerical data and textual identifiers for theplurality of user-selected items from the plurality of differentfinancial databases.
 12. The electronic device of claim 11 wherein thecross-reference icon provides a pop-up window comprising a plurality oftabs for accessing the numerical data and textual identifiers inrespective different financial databases associated to the numericaldata and textual identifiers in the current menu.
 13. The electronicdevice of claim 11 wherein each menu comprises a plurality of fiscalyear indicators for providing different numerical data and textualidentifiers for each fiscal year.
 14. The electronic device of claim 11wherein each menu comprises a home screen providing a general overviewof the different numerical data and textual identifiers for thecorresponding different financial database.
 15. The electronic device ofclaim 11 wherein the plurality of different financial databasescomprises a planning database, a budget database, an accountingdatabase, a personnel database, and a contracts database.
 16. Theelectronic device of claim 15 wherein the menu for the budget databasecomprises a plurality of tabs for accessing a plurality of versions of abudget.
 17. The electronic device of claim 11 wherein said GUI comprisesa plurality of tabs for selecting the plurality of menus for accessingthe different numerical data and textual identifiers for the pluralityof different financial databases.
 18. The electronic device of claim 11wherein the different numerical data and textual identifiers comprise amonetary cost and item description.
 19. The electronic device of claim11 wherein said GUI comprises a web page based user interface.
 20. Theelectronic device of claim 11 wherein the plurality of differentfinancial databases comprises an Office of Program Policy Analysis andGovernment Accountability (OPPAGA) database, a LegislativeAppropriations System (LAS)/Planning Budget Subsystem (PBS) database, aFlorida Accounting Information Resource Subsystem (FLAIR) database, anda People First Subsystem (PFS) database